SPEC-ERD-FLD · v0.2 14 June 2026 Owner: Platform team
Field — data model drill-down
The entities behind field.riversync.com: the on-site Visit and everything captured against it — runbook tasks, parts, evidence, the customer sign-off — plus the per-device maintenance plans that drive preventive work. The execution half of service operations.
DraftRenders from the central catalog
Drill-down of the master ERD. Requirements: SPEC-APP-FLD (FLD-1…10) + master SPEC-PRD. Entities and DM-rules render from erd/erd-entities.js — definitions are never copied per document. The Field service (SPEC-DDD-FLD) owns this cluster.
1The on-site visit
Sources: FLD-1…9 · DM-27…31 · prototype: the Field mobile app (dispatch → check-in → runbook → parts/evidence → sign-off).FLD-D1
RiverSync Co., Ltd. · BangkokSPEC-ERD-FLD · 1 of 2
2Scheduling the visit
Before a visit lands on the board it is scheduled by negotiation: RiverSync — or, for the devices it services, the assigned servicing partner — proposes candidate slots, the customer selects one, and the accepted slot creates the Visit. Field owns the proposal records and the customer's standing preferences; the surfaces are Admin (propose / dispatch), Portal (select) and Partners (the servicing partner works its assigned visits within scope, DM-59). Process detail: SPEC-PWF-SCH.
The Visit is the bridge between three domains it does not own: a ServiceTicket (Support) for corrective work, a Device and its OrganizationSite (Devices & Structure) for context and arrival info, and the assigned engineer account (Identity). Field owns only the execution records.
The shared service cluster — ticket → visit → thread — seen from Support. The same Visit is executed in Field. Portal drill-down shows it customer-side.FLD-D2
4Conditions in play
The DM-rules that bind this app's surfaces — rendered from the central catalog; the master holds the full set.
5Revision history
Version
Date
Changes
0.1
14 Jun 2026
First drill-down — Field joins the ERD set (SPEC-ERD v0.12). Visit extended (Kind, Status, CheckInAt…); VisitTask · PartUsed · VisitEvidence · VisitSignoff · MaintenancePlan added; DM-27…31; fieldservice diagram; Visit ownership moved Support → Field
0.2
29 Jun 2026
Service scheduling cluster added (SPEC-ERD v0.27). New §2 with the scheduling diagram — VisitProposal · VisitProposalOption · SchedulingPreference → Visit (Visit gains ProposalId); rules DM-57…59. Field owns scheduling (SVC-20); surfaces are Admin (ADM-7, propose), Portal (PTL-11, accept), Partners (PAR-15, read-only). Process: SPEC-PWF-SCH. Later sections renumbered §3–§5.
RiverSync Co., Ltd. · BangkokSPEC-ERD-FLD · 2 of 2
